Skip to content

chore(deps): update dependency packaging to v26.3 - #255

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/packaging-26.x
Open

chore(deps): update dependency packaging to v26.3#255
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/packaging-26.x

Conversation

@renovate

@renovate renovate Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
packaging ==26.2==26.3 age adoption passing confidence

Release Notes

pypa/packaging (packaging)

v26.3

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — trivial dev dependency patch bump.

Extended reasoning...

Overview

Single-line change to requirements-dev.txt, bumping the pinned packaging version from 26.2 to 26.3 (a patch release). This is an autogenerated lockfile maintained by pip-compile, and packaging is a transitive dev/test dependency (used by pytest and sphinx), not a runtime dependency of pyUSPTO itself.

Security risks

None. No production code, auth, crypto, or permission logic is touched. packaging is a well-maintained, widely-used PyPI metadata-parsing library; a patch bump carries negligible risk.

Level of scrutiny

Minimal scrutiny warranted — this is a mechanical, bot-generated dependency lockfile update with a single line diff and no functional code changes.

Other factors

No CODEOWNERS or critical paths involved. No outstanding review comments on the PR. Renovate-generated PRs of this shape are routine and safe to auto-approve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants